README CITP v4.11

README.HTM for Crescent Internet ToolPak(tm) Version 4.12
Copyright (c) 1995-2000 Progress Software Corporation. All rights reserved.

Introduction

Reference: See http://www.microsoft.com for the latest Microsoft Service Packs and Updates

B. Deploying Your Applications

For an explanation on how to deploy and distribute your application, see the Crescent Internet ToolPak 4.12 Help File Introduction. Read the topic 'File Distribution/Application Deployment'.

Note: If your application uses the high-level CIFTP methods GetDirectory, GetFile, or PutFile, you will need to include the wininet.dll with your distributed application. This dll has special installation requirements. Please refer to the Microsoft knowledge base (http://www.microsoft.com) article Q185375 for information on installing this dll properly.

C. PDQComm Users

It is recommended that PDQComm 3.0 users upgrade to version 3.4 or higher to avoid licensing issues. We have included an emulator version of the PDQComm control and a full licensed version of the Tapi control. Version 3.4 contains the latest bug
fixes.

1.	The ITP Mail Wizard Add-In does not work in VB5/6.
2.	Do not stop a MIME decode; if you do, a memory leak will occur. Resources do not get released when a program is stopped in the VB environment. We recommend that you do not interrupt the code during execution.
3.	If no RAS entries exist when you install NT 4.0 for the first time, the thread for the CIRAS control hangs. Workaround: If you are creating a project requiring RAS entries, perform the following steps: Place a listbox on the form (name i.e. PhoneEntries). Add this code: Set FrmServer.RasControl.ListBoxName = PhoneEntries FrmServer.RasControl.RASEnumEntries
4.	A registration issue exists for the CIRAS control (NT issue only). If you do not install dial-up networking before you install Internet ToolPak 4.12, a message appears during the installation and the control does not register. This does not happen on Windows 95. RAS is implemented differently on Windows 95 than it is on Windows NT.
5.	Microsoft Knowledge Base Article Q168348 states that RAS Dial Up leaks resources on Microsoft Windows NT Workstation version 4.0 and Microsoft Windows NT Server version 4.0. This is not a defect in our RAS control; it is a known issue with NT 4.0. The Win32 API RAS APIs used for connection management do not de-allocate all of the memory they use. Any process that repeatedly establishes and removes connections causes an increased use of memory and resources. This resource drain might prevent RAS from dialing out.
6.	The CIMIME design time properties dialog box incorrectly lists the SourceFileSize and DestinationFileSize properties. These properties are available only at runtime.
7.	The CIRAS control's Hostavailable method fails to find a valid host when you firsr write a new project. The control begins to work when you reload the project, load another project, or add another Crescent Internet ToolPak control. To work around this, place a CITCP control on the form. You do not need to write code.
8.	The TAPI control incorrectly states in its About box that it is for design time only. The control is licenced for full functionality.
9.	Users who have VB5 or VB6 on their machine may see problems running the HTTP FormParsing Demo. When you type in a url, it may generate a message if it finds a site with a form to display. Should this happen you will need the VB4 file VEN2232.OLB Version 2.2 from Visual Basic 4.0. This should be placed in your System directory on Win95 or System32 on NT 4.0.

Part 3: Technical Support

The Crescent technical support staff is ready to help you with problems that you encounter when installing or using Internet ToolPak 4.12. The Crescent technical support staff will do its best to help you succeed with Internet ToolPak 4.12.

A. Technical Support Options